On-demand storage system energy savings

ABSTRACT

Embodiments of the invention relate to dynamic power management of storage volumes and disk arrays in a storage subsystem to mitigate loss of performance resulting from the power management. The volumes and arrays are prioritized, and in real-time power is selectively reduced in response to both the prioritization and an energy savings goal. A feedback loop is provided to dynamically measure associated power gain based upon a lowering of power consumption, and device selection may be adjusted based upon received feedback.

BACKGROUND

This invention relates to on-demand power reduction with a storagesubsystem of a data site. More specifically, the invention relates topower management of storage elements within the data center thatminimizes loss of performance with respect to data access.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computerresources, e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services, that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of service. One of the characteristics ofcloud computing infrastructure is that applications can be launched froma plurality of locations with each location referred to herein as a datasite. Executing applications and processing data responsive to theapplication execution consumes power, which in some circumstances needsto be regulated. Power reduction may occur on a periodic or temporarybasis. A periodic basis pertains to power reduction coming at a setfrequency, and a temporary basis pertains to a reduction that is not ona set frequency. Power reduction of a data site may be required forcircumstances external to power delivery. For example, power reductionmay be necessary due to failure of an external cooling mechanism. In oneembodiment, periodic power reductions can be accounted for with greaterprecision than temporary power reductions. One common element withrespect to power consumption is the need to maintain a level ofperformance that allows for uninterrupted data processing and access tocomputer resources.

For each category of power reduction, there is a need to balance powerallocation and performance of applications and associated dataprocessing. In one embodiment, the aspect of balancing may mean that thepower reduction target is reached, while minimizing performance loss ondata access to the storage system(s). Accordingly, balancing power in acomputing environment is challenging.

BRIEF SUMMARY

This invention comprises a method, system, and article for creation ofconsistent data within an on-demand network accessible environment witha shared pool of configurable computing resources.

In one aspect, a method is provided for on-demand power reduction withina storage subsystem of a data center having multiple storage devicesorganized in a hierarchy. Power consumption of the storage devices ismonitored and reported. In addition, data access performance associatedwith each of the storage devices is monitored and reported. The dataaccess performance monitoring and performance includes storing policiesof the storage devices. At such time as a request to limit powerconsumption is received, a set of heuristics are in receipt of thereport(s) and lower power usage of at least one storage device in thesubsystem by a required amount while maintaining performance of thestorage subsystem based upon the stored policies. The heuristics operatein real-time to select one of the devices in the hierarchy. The powerconsumption setting of the selected device is lowered based upon anassociated priority setting. Power consumption feedback is measuredafter lowering the power consumption setting of the selected device. Thedevice selection may be adjusted according to the measured feedback.

In a further aspect, a system is provided with a storage subsystem of adata center having multiple storage devices, including at least onestorage volumes and at least one disk array, with the devices organizedin a hierarchy. A functional unit is provided in communication with thestorage subsystem. The functional unit includes tools to support dynamicpower management of the storage devices. More specifically, thefunctional unit includes a storage device manager, a data accessmanager, and a power manager. The storage device manager monitors andreports power consumption of the storage devices. The data accessmanager, which is in communication with the storage device manager,monitors and reports data access performance with respect to each of thestorage devices. In addition, the data access manager stores policiespertaining to the storage devices. The power manager, which is incommunication with the storage device and data access managers, employsa set of heuristics to receive the report(s) from the storage device anddata access managers and lowers power usage of one or more storagedevice in response to a power limit request while maintainingperformance in compliance with the storage policies. In one embodiment,the heuristics operate in real-time. More specifically, a first of theheuristics selects a device in the hierarchy based upon a prioritysetting, and lowers a power consumption setting thereof. A second of theheuristics measures feedback pertaining to the power consumption afterthe adjustment by the first heuristic is complete. An adjustment ofdevice selection may be implemented based upon the measured feedback.

In a further aspect, a computer program product is provided for use witha storage subsystem of a data center. The storage subsystem includesmultiple storage devices, including one or more volumes and one or moredisk arrays, organized in a hierarchy. The computer program productcomprises a computer readable storage medium having computer readableprogram code embodied therewith. Computer readable program code isprovided to monitor and report power consumption of the storage devices,and to monitor and report data access performance on each of the storagedevices. In one embodiment, the program code stores policies associatedwith the storage devices. Program code is provides to respond to arequest to limit power associated with the storage devices. Morespecifically, the program code receive the report(s) and employs a setof real-time heuristics to lower power usage of at least one storagedevice in the subsystem while maintaining performance of the subsystembased upon the stored policies. A first heuristic selects a devicewithin the hierarchy, based upon a priority setting, and lowers a powerconsumption setting for the selected device. A second heuristic measurespower consumption feedback after lowering the power consumption of theselected device. The selection of devices may be adjusted based upon themeasured feedback.

In an even further aspect, a computer implemented method is provided tosupport energy savings in a data center having multiple storage devicesorganized in a hierarchy. Following a request to limit powerconsumption, power usage of at least one of the devices is dynamicallylowered by a required amount. At the same time, performance of the datacenter is maintained to comply with stored policies of the storagedevices, while minimizing performance loss. The aspect of dynamic powermanagement includes selection of a device in the hierarchy based uponits priority setting and lowering a power consumption setting of theselected device. Feedback in the form of measured power consumption ismaintained so that the selection of devices may be adjusted.

Other features and advantages of this invention will become apparentfrom the following detailed description of the presently preferredembodiment of the invention, taken in conjunction with the accompanyingdrawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The drawings referenced herein form a part of the specification.Features shown in the drawings are meant as illustrative of only someembodiments of the invention, and not of all embodiments of theinvention unless otherwise explicitly indicated.

FIG. 1 depicts a cloud computing node according to an embodiment of thepresent invention.

FIG. 2 depicts a cloud computing environment according to an embodimentof the present invention.

FIG. 3 depicts abstraction model layers according to an embodiment ofthe present invention.

FIG. 4 depicts a flow chart illustrating a process for throttling avolume within data storage.

FIG. 5 depicts a flow chart illustrating a process for computing bothpower gain and performance loss on switching the power state of a diskarray.

FIG. 6 depicts a flow chart illustrating a feedback control loop formanagement of volume(s) and/or disk array(s).

FIG. 7 depicts a block diagram illustrating tools embedded in a computersystem to support dynamic power management of disk arrays and/or volumeswithin a data site.

FIG. 8 depicts a block diagram showing a system for implementing anembodiment of the present invention.

DETAILED DESCRIPTION

It will be readily understood that the components of the presentinvention, as generally described and illustrated in the Figures herein,may be arranged and designed in a wide variety of differentconfigurations. Thus, the following detailed description of theembodiments of the apparatus, system, and method of the presentinvention, as presented in the Figures, is not intended to limit thescope of the invention, as claimed, but is merely representative ofselected embodiments of the invention.

The functional units described in this specification have been labeledas managers. A manager may be implemented in programmable hardwaredevices such as field programmable gate arrays, programmable arraylogic, programmable logic devices, or the like. The managers may also beimplemented in software for processing by various types of processors.An identified manager of executable code may, for instance, comprise oneor more physical or logical blocks of computer instructions which may,for instance, be organized as an object, procedure, function, or otherconstruct. Nevertheless, the executable of an identified manager neednot be physically located together, but may comprise disparateinstructions stored in different locations which, when joined logicallytogether, comprise the managers and achieve the stated purpose of themanagers.

Indeed, a manager of executable code could be a single instruction, ormany instructions, and may even be distributed over several differentcode segments, among different applications, and across several memorydevices. Similarly, operational data may be identified and illustratedherein within the manager, and may be embodied in any suitable form andorganized within any suitable type of data structure. The operationaldata may be collected as a single data set, or may be distributed overdifferent locations including over different storage devices, and mayexist, at least partially, as electronic signals on a system or network.

Reference throughout this specification to “a select embodiment,” “oneembodiment,” or “an embodiment” means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment of the present invention. Thus,appearances of the phrases “a select embodiment,” “in one embodiment,”or “in an embodiment” in various places throughout this specificationare not necessarily referring to the same embodiment.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided, such asexamples of an application manager, a replication manager, a migrationmanager, etc., to provide a thorough understanding of embodiments of theinvention. One skilled in the relevant art will recognize, however, thatthe invention can be practiced without one or more of the specificdetails, or with other methods, components, materials, etc. In otherinstances, well-known structures, materials, or operations are not shownor described in detail to avoid obscuring aspects of the invention.

The illustrated embodiments of the invention will be best understood byreference to the drawings, wherein like parts are designated by likenumerals throughout. The following description is intended only by wayof example, and simply illustrates certain selected embodiments ofdevices, systems, and processes that are consistent with the inventionas claimed herein.

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes. Referring now to FIG. 1, a schematic ofan example of a cloud computing node is shown. Cloud computing node (10)is only one example of a suitable cloud computing node and is notintended to suggest any limitation as to the scope of use orfunctionality of embodiments of the invention described herein.Regardless, cloud computing node (10) is capable of being implementedand/or performing any of the functionality set forth hereinabove. Incloud computing node (10) there is a computer system/server (12), whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server (12) include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server (12) may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server (12) may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server (12) in cloud computing node(10) is shown in the form of a general-purpose computing device. Thecomponents of computer system/server (12) may include, but are notlimited to, one or more processors or processing units (16), a systemmemory (28), and a bus (18) that couples various system componentsincluding system memory (28) to processor (16). Bus (18) represents oneor more of any of several types of bus structures, including a memorybus or memory controller, a peripheral bus, an accelerated graphicsport, and a processor or local bus using any of a variety of busarchitectures. By way of example, and not limitation, such architecturesinclude Industry Standard Architecture (ISA) bus, Micro ChannelArchitecture (MCA) bus, Enhanced ISA (EISA) bus, Video ElectronicsStandards Association (VESA) local bus, and Peripheral ComponentInterconnects (PCI) bus. Computer system/server (12) typically includesa variety of computer system readable media. Such media may be anyavailable media that is accessible by computer system/server (12), andit includes both volatile and non-volatile media, removable andnon-removable media.

System memory (28) can include computer system readable media in theform of volatile memory, such as random access memory (RAM) (30) and/orcache memory (32). Computer system/server (12) may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system (34) can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus (18) by one or more datamedia interfaces. As will be further depicted and described below,memory (28) may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility (40), having a set (at least one) of program modules(42), may be stored in memory (28) by way of example, and notlimitation, as well as an operating system, one or more applicationprograms, other program modules, and program data. Each of the operatingsystems, one or more application programs, other program modules, andprogram data or some combination thereof, may include an implementationof a networking environment. Program modules (42) generally carry outthe functions and/or methodologies of embodiments of the invention asdescribed herein.

Computer system/server (12) may also communicate with one or moreexternal devices (14), such as a keyboard, a pointing device, a display(24), etc.; one or more devices that enable a user to interact withcomputer system/server (12); and/or any devices (e.g., network card,modem, etc.) that enable computer system/server (12) to communicate withone or more other computing devices. Such communication can occur viaInput/Output (I/O) interfaces (22). Still yet, computer system/server(12) can communicate with one or more networks such as a local areanetwork (LAN), a general wide area network (WAN), and/or a publicnetwork (e.g., the Internet) via network adapter (20). As depicted,network adapter (20) communicates with the other components of computersystem/server (12) via bus (18). It should be understood that althoughnot shown, other hardware and/or software components could be used inconjunction with computer system/server (12). Examples, include, but arenot limited to: microcode, device drivers, redundant processing units,external disk drive arrays, RAID systems, tape drives, and data archivalstorage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment (50)is depicted. As shown, cloud computing environment (50) comprises one ormore cloud computing nodes (10) with which local computing devices usedby cloud consumers, such as, for example, personal digital assistant(PDA) or cellular telephone (54A), desktop computer (54B), laptopcomputer (54C), and/or automobile computer system (54N) may communicate.Nodes (10) may communicate with one another. They may be grouped (notshown) physically or virtually, in one or more networks, such asPrivate, Community, Public, or Hybrid clouds as described hereinabove,or a combination thereof. This allows cloud computing environment (50)to offer infrastructure, platforms and/or software as services for whicha cloud consumer does not need to maintain resources on a localcomputing device. It is understood that the types of computing devices(54A)-(54N) shown in FIG. 2 are intended to be illustrative only andthat computing nodes (10) and cloud computing environment (50) cancommunicate with any type of computerized device over any type ofnetwork and/or network addressable connection (e.g., using a webbrowser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment (50) (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided: hardware and software layer (60),virtualization layer (62), management layer (64), and workload layer(66). The hardware and software layer (60) includes hardware andsoftware components. Examples of hardware components include mainframes,in one example IBM® zSeries® systems; RISC (Reduced Instruction SetComputer) architecture based servers, in one example IBM pSeries®systems; IBM xSeries® systems; IBM BladeCenter® systems; storagedevices; networks and networking components. Examples of softwarecomponents include network application server software, in one exampleIBM WebSphere® application server software; and database software, inone example IBM DB2® database software. (IBM, zSeries, pSeries, xSeries,BladeCenter, WebSphere, and DB2 are trademarks of International BusinessMachines Corporation registered in many jurisdictions worldwide).

Virtualization layer (62) provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer (64) may provide the followingfunctions: resource provisioning, metering and pricing, user portal,service level management, and SLA planning and fulfillment. Thefunctions are described below. Resource provisioning provides dynamicprocurement of computing resources and other resources that are utilizedto perform tasks within the cloud computing environment. Metering andpricing provides cost tracking as resources are utilized within thecloud computing environment, and billing or invoicing for consumption ofthese resources. In one example, these resources may compriseapplication software licenses. Security provides identity verificationfor cloud consumers and tasks, as well as protection for data and otherresources. User portal provides access to the cloud computingenvironment for consumers and system administrators. Service levelmanagement provides cloud computing resource allocation and managementsuch that required service levels are met. Service Level Agreement (SLA)planning and fulfillment provides pre-arrangement for, and procurementof, cloud computing resources for which a future requirement isanticipated in accordance with an SLA.

Workloads layer (66) provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer includes, but is notlimited to: mapping and navigation; software development and lifecyclemanagement; virtual classroom education delivery; data analyticsprocessing; operation processing; and maintenance of data processingprioritization to support power management within the cloud computingenvironment.

In the shared pool of configurable computer resources described herein,hereinafter referred to as a cloud computing environment, files may beshared among users within multiple data centers, also referred to hereinas data sites. There is a challenge associated with achieving efficientand on-demand energy savings at the data site. More specifically,current models of power management do not address real-time techniquesthat account for mitigation of performance impact on data processing.The following is a description of data storage and one or more tools tosupport real-time power management of storage elements. Data storageunits are categorized into two tiers, including disk arrays and volumes.A disk array is a physical group of volumes. In one embodiment, the diskarray is labeled with the priority of its highest priority volume,wherein a volume is a data storage device. A computer recognizes alldata storage devices as volumes. In one embodiment, each volume has anassociated file system recognizable by the computer and also has anassociated priority. A control system uses a demand response heuristicto determine to which system component to send control commands to thetwo tiers of storage units to trigger corresponding on-demand powercapping capabilities. More specifically, energy consumption of a diskarray or volume is reduced on a temporary basis while minimizingperformance impact, and without migrating data or denying data access.The demand response heuristic uses power and performance measurements asinput and refers to a set of performance and power models to predict theimpact of control commands. To compensate for inaccuracy in the models,a feedback driven control loop is employed.

There are two categories of data storage facilities, including a volumebased facility and a disk array based facility. The act of throttlingslows down selected I/O streams. More specifically, energy savings maybe achieved by slowing down the rate at which the volume processes anI/O stream. A volume based facility is known to limited input and output(I/O) rates of chosen volumes to reduce the intensity of a machineworkload measured in I/O operations per second (IOPS). This intensityreduction generally results in reducing energy consumption of the diskarrays in which these volumes reside. A per-volume throttling of I/Osupports fine grained and continuous control that enables a search foran optimal amount of throttling such that the sum of a resulting powersavings meets a set target. The disk array based facility allowsselected disk arrays to enter a low power state with associated recoverylatency. In one embodiment, the disk array is labeled with the priorityof its highest priority volume. Through use of the volume and disk arraybased storage facilities, the goal is to decide which volumes tothrottle and which disk arrays to switch to low power state such thatthe demand response power target is met while the performance loss ofhigh priority data access is minimized. Accordingly, power savings isachieved with respect to data storage on one or both of the volume andthe disk array through throttling and adjustment of the power state,respectively.

FIG. 4 is a flow chart (400) illustrating a process for throttling avolume within data storage. Specifically, the data storage may includeone or more volumes of storage media, with each volume assigned arespective priority level. In one embodiment, the priority level isassociated with the relative importance of operability of the volumewith respect to other volumes in data storage. The variable P_(Total) isassigned to the quantity of priority levels identified in the volumes(402), and the counting variable P for each priority level is assignedto the integer one (404). For priority level P, the variable N_(Total)is assigned to the quantity of volumes at priority level P (406), andthe counting variable N for each volume at priority P is assigned to theinteger one (408). For each volume N at priority P, the power savings bythrottling volume N is computed (410). In one embodiment, power savings,E (TO) is achieved by throttling the volume N until its IO per secondreaches a minimal utilization permitted by an associated policy. At thesame time, the performance loss by throttling volume N at priority P iscomputed (412), and the performance loss in terms of the change inresponse time by throttling volume N at priority P is computed (414).The performance being monitored can include, but is not limited to,response time and throughput. As shown at step (412), performance lossis calculated in terms of throughput as the change in IO. Similarly, asdemonstrated at step (414), performance loss can be computed as a changein response time, RT.

Following step (414), the variable N, representing the quantity ofvolumes at priority level P, is incremented (416). It is then determinedif there are additional volumes at priority P to be evaluated (418). Anegative response to the determination at step (418) is followed by areturn to step (410). Conversely, a positive response to thedetermination at step (418) is followed by an increment of the variableP (420), with P representing the priority level subject to evaluation. Asecond determination then takes place to ascertain if there areadditional priority levels and volumes assigned to such levels that needto be evaluated (422). A negative response to the determination at step(422) is followed by a return to step (406), and a positive response tothe determination at step (422) concludes the calculation of the powersavings, performance loss, and power gain associated with throttlingindividual storage volumes. Accordingly, for each volume and eachpriority level, the power savings, performance loss and response timesavings may be calculated.

As explained above, a disk array is a physical group of volumes whereinan entire disk array, and the volumes encompassed therein, may be placedin a low power state to provide energy savings. However, such savings dohave a price. FIG. 5 is a flow chart (500) illustrating the process ofcomputing both power gain and performance loss on switching the powerstate of a disk array. A priority level for the disk array is set topriority level P (502). The set of disk arrays in normal operating statewith priority level P is represented as R(P) (504), the variableM_(Total) is assigned to the quantity of disk arrays at priority level P(506), and a counting variable M is set to the integer one (508). Thepower gain associated with switching the disk array R_(M) (P) fromnormal to a low power state is computed (510). In one embodiment, thepower gain or change of power is represented as ΔE (Disk Array_(m)).Additionally, the performance loss, ΔRT_(M) (P), with switching the diskarray R_(M) (P) from normal to a low power state is computed (512).Following the computations at steps (510) and (512), the variable M isincremented (514), and it is then determined if each of the disk arraysat priority level P have been evaluated (516). A negative response tothe determination at step (516) is followed by a return to step (510).Conversely, a positive response to the determination at step (516)concludes the power gain and performance loss computations. Accordingly,for each disk array at a set priority level, the power gain andperformance loss may be calculated.

As stated above, the goal of the calculation is to determine whichvolumes to throttle and which disk arrays to place in a low power state,all the while mitigating performance degradation. The following ispseudo code for selection of a volume or disk arrays for throttling orplacing in a low power state, respectively:

For each volume:

-   -   Calculate energy gain efficiency per IO per second sacrificed on        a disk array basis and a volume basis. For the disk array basis,        calculate the ratio of ΔE (disk array)/ΔIO, or energy gain        efficiency per IO per second sacrificed. For the volume basis,        calculate the ratio of ΔE (volume)/ΔIO, where ΔIO is the change        in the rate of IO per second;    -   Calculate response time sacrificed on a disk array basis and a        volume basis. For the disk array basis, calculate the ratio of        ΔE (disk array)/ΔRT (disk array). For the volume basis,        calculated the ratio of ΔE (volume)/ΔRT (volume).    -   If a volume, V, is selected:        -   Update volume, V, as to be throttled;        -   ΔE=ΔE+ΔE (volume);    -   Else, if a disk array, R, is selected:        -   Update disk array R, as to be throttled;        -   ΔE=ΔE+ΔE (disk array);            Accordingly, as demonstrated, a value may be attached to the            energy savings.

Both the volumes and disk arrays may be manipulated to meet energysavings goals. The energy savings goal may be a long term commitment ora short term commitment. Once the demand response has reached the end ofthe term, power may be restored to all disk arrays placed in a loweredpower state. Similarly, the throttling may be removed from all volumesaffected by the throttling. Accordingly, the adjustments imposed on thehardware to attain the power savings may be for a limited period oftime, followed by restoration of power.

It is recognized that there may be inaccuracy associated with a shift inworkload characteristics after the described low powering actions havetaken place. Volumes selected for throttling, or disk arrays selectedfor throttling of volumes and/or a lowered power state may yield agreater savings than anticipated or not enough savings. To address thislimitation, a feedback control loop is employed where energy savingsadjustments on the volumes and/or disk arrays are measured with respectto the energy savings goals.

FIG. 6 is a flow chart (600) illustrating a feedback control loop formanagement of volume(s) and/or disk array(s). As shown, a power level,P, is set to designate volumes and disk arrays operating at this levelas being available for adjustment (602). It is then determined if thereare any volumes or disk arrays available at power level P (604). Anegative response to the determination at step (604) is followed by anew power level designation (606) followed by a return to step (604).Conversely, a positive response to the determination at step (604) isfollowing by adjusting one volume or disk array at power level P (608),measuring the associated power gain in response to the adjustment (610),and updating the demand response (612). Accordingly, each adjustment,also referred to herein as an iteration, is followed by an update of thedemand response of the system.

Following step (612), it is determined if the adjustment at step (608)exceeded the energy savings goal (614). A positive response to thedetermination at step (614) is following by termination of the feedbackheuristic (616). Conversely, a negative response to the determination atstep (614) is followed by determining if there is another disk array orvolume at priority P that is available for adjustment (618). A positiveresponse to the determination at step (618) is followed by a return tostep (608), and a negative response is followed by changing the powerlevel P (620) followed by a return to step (604). Accordingly, thephased heuristic shown herein provides an opportunity to obtain powerconsumption feedback after some volumes or disk array have beenthrottled or low powered, respectively, and further volume and diskarray adjustments may be made according to the feedback.

Although not reflected in the figures shown herein, the demand toaddress energy savings may be based upon time duration. Once the timeduration has passed, the limits on all the volumes may be removed andpower may be restored to all disk arrays that were placed in a low powerstate.

Example

The following is an example of a system with two disk arrays and twovolumes in each disk array. Disk array₁ has Volume₁ and Volume₂, andDisk array₂ has Volume₃ and Volume₄. Volume₁ has a priority level ofone, an TOPS rate of 150, and a minimum TOPS rate of 25. Volume₂ has apriority level of 3, an TOPS rate of 50, and a minimum TOPS rate of 25.Volume₃ has a priority level of 3, an TOPS rate of 150, and a minimumTOPS rate of 25. Volume₄ has a priority level of 4, an TOPS rate of 50,and a minimum TOPS rate of 25. Both disk arrays have the same powermodel. The energy savings, ΔE, goals is 10 watts, and the priority levelP is set to 4. Only Volume₄ is eligible for throttling at this prioritylevel, and no disk array is eligible for low powering at this prioritylevel. Volume₄ is throttled and ΔE is assessed at 0.5 Watts, which isless than the goal of 5 Watts. Next, the priority level is changed to 3.Volume₂ and Volume₃ both have a priority level of 3, as does Diskarray₂. Low powering Disk array₂ yield a power gain of 4 Watts and hasno TOPS loss. Therefore Disk array₂ is low-powered, which yields a totalenergy savings, ΔE, of 4.5 Watts, which is still less than the goal.However, at priority level 3, two volumes are eligible for throttling,Volume₂ and Volume₃. Volume₂ yields 2 Watts of energy savings at theexpense of 50 TOPS and Volume₃ yields 1 Watt of energy savings at theexpense of 100 IOPS. Accordingly, Volume₂ is throttled, yielding anenergy savings, ΔE, of 6.5 Watts, which is greater than the goal.

As demonstrated in the flow charts of FIGS. 1-6 and the associatedexample, a method is employed to support on-demand power reductionwithin storage subsystems of a data site. The power to the volumesand/or disk arrays in the data site is dynamically adjusted on atemporary basis to provide a balanced energy reduction while minimizedoverall performance impact on the storage subsystems. FIG. 7 is a blockdiagram (700) illustrating tools embedded in a computer system tosupport dynamic power management of disk arrays and/or volumes within adata site. A shared pool of configurable computer resources is shownlocal to a first data site (710). Although only one data site is shownin the example herein, the invention should not be limited to a singledata site and may be expanded to include a plurality of data sites. Thedata site (710) is provided with at least one server (720) incommunication with data storage (728). The server (720) has a processingunit (722), in communication with memory (724) across a bus (726), andin communication with data storage (728). As shown herein, data storage(728) includes two disk arrays (730) and (732), and two storage volumes(734) and (736). In one embodiment, the quantity of disk arrays andstorage volumes may differ, and as such, the invention should not belimited to the quantity shown herein.

In the example shown herein, a functional unit (740) is provided localto the server (720) and in communication with the data storage (728) tomanage power consumption of the storage entities (730)-(736). Morespecifically, the functional unit (740) has tools in the form ofmanagers to support power management within the data storage (728). Thetools include, but are not limited to, a storage device manager (742), adata access manager (744), and a power manager (746). The storage devicemanager (742) is provided to monitor and report power consumption of thephysical storage devices in data storage (728). The data access manager(744) is provided to monitor and report data access performance withrespect to each of the physical storage devices in data storage (728)and to store policies pertaining to the storage devices (728). Thestored policies include, but are not limited to priorities, responsetime targets, and throughput targets. The power manager (746) isprovided in communication with both the storage device manager (742) andthe data access manager (744). The power manager (746) is responsiblefor receiving reporting data from both the storage device manager (742)and the data access manager (744) and employing heuristics in real-timeto mitigate power consumption by the storage devices. More specifically,in response to a request or another form of communication indicating arequirement to reduce power consumption, the power manager (746) bothlowers power usage while maintaining performance of the data storage incompliance with stored performance policies. Accordingly, the managers(742)-(746) of the functional unit (740) address power management ofstorage elements while addressing performance policies.

Two heuristics are provided to support the goals and functionality ofthe power manager (746). A first heuristic organizes the storage devicesin a hierarchy, with the arrangement including both disk arrays andvolumes. The first heuristic selects one of the devices in thearrangement and lowers a power consumption setting based upon a prioritysetting thereof. A second heuristic measures a power consumptionfeedback following the lowering of the power consumption setting of theselected storage device. More specifically, the second heuristic makesadjustment to a selection of the storage devices according to themeasured feedback.

As described above, there are two methods of managing power output fromthe storage devices as directed by the power manager (746), includingthrottling, i.e. reducing, I/O rates to one or more storage volumes, andplacing a disk array in a low power state. In one embodiment, the powermanagement may concurrently execute both methods, meaning lowering apower state of a disk array while throttling a volume. The management ofthe power consumption of the storage elements is conducted in a dynamicmanner. In one embodiment, the power consumption is adjusted on atemporary basis in an effort to minimize overall performance impactoriginating from the storage elements. For example, once the request tolimit power has elapsed, the power manager (746) may remove the powerconsumption limitations on the volumes and/or disk arrays. As discussedabove, the data storage elements are arranged in a hierarchy. Theheuristics employed by the power manager (746) address power consumptionadjustment in order of priority. More specifically, those volumes and/orarrays with a low priority setting are adjusted before volumes and/orarrays with a higher priority setting. Accordingly, by making theadjustments responsive to the hierarchy, power savings is attained whilemitigating impact on read and write transactions to the data storage.

Power consumption and associated management of storage elements aresupported by the storage device manager (742), data access manager(744), and power manager (746) of the functional unit (740). In oneembodiment, the managers are provided in the shared pool of configurablecomputer resources, i.e. cloud, to arrange the data elements in ahierarchy and to throttle one or more storage volumes and/or place oneor more disk arrays into a lower power state responsive to both thehierarchy and the power management requirements. The storage devicemanager (742), data access manager (744), and power manager (746) of thefunctional unit (740) are shown residing in memory (724) of the server(720) local to the first data site (710). Although in one embodiment,the managers may reside as hardware tools external to memory (724), orthey may be implemented as a combination of hardware and software.Similarly, in one embodiment, the managers may be combined into a singlefunctional item that incorporates the functionality of the separateitems. As shown herein, each of the manager(s) is shown local to onedata site. However, in one embodiment they may be collectively orindividually distributed across a shared pool of configurable computerresources and function as a unit to manage creation of identicalconsistency points in two different file systems. Accordingly, themanagers may be implemented as software tools, hardware tools, or acombination of software and hardware tools.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remoteor separate computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider).

Aspects of the present invention are described above with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

Referring now to FIG. 8 is a block diagram (800) showing a system forimplementing an embodiment of the present invention. The computer systemincludes one or more processors, such as a processor (802). Theprocessor (802) is connected to a communication infrastructure (804)(e.g., a communications bus, cross-over bar, or network). The computersystem can include a display interface (806) that forwards graphics,text, and other data from the communication infrastructure (804) (orfrom a frame buffer not shown) for display on a display unit (808). Thecomputer system also includes a main memory (810), preferably randomaccess memory (RAM), and may also include a secondary memory (812). Thesecondary memory (812) may include, for example, a hard disk drive (814)and/or a removable storage drive (816), representing, for example, afloppy disk drive, a magnetic tape drive, or an optical disk drive. Theremovable storage drive (816) reads from and/or writes to a removablestorage unit (818) in a manner well known to those having ordinary skillin the art. Removable storage unit (818) represents, for example, afloppy disk, a compact disc, a magnetic tape, or an optical disk, etc.,which is read by and written to by removable storage drive (816). Aswill be appreciated, the removable storage unit (818) includes acomputer readable medium having stored therein computer software and/ordata.

In alternative embodiments, the secondary memory (812) may include othersimilar means for allowing computer programs or other instructions to beloaded into the computer system. Such means may include, for example, aremovable storage unit (820) and an interface (822). Examples of suchmeans may include a program package and package interface (such as thatfound in video game devices), a removable memory chip (such as an EPROM,or PROM) and associated socket, and other removable storage units (820)and interfaces (822) which allow software and data to be transferredfrom the removable storage unit (820) to the computer system.

The computer system may also include a communications interface (824).Communications interface (824) allows software and data to betransferred between the computer system and external devices. Examplesof communications interface (824) may include a modem, a networkinterface (such as an Ethernet card), a communications port, or a PCMCIAslot and card, etc. Software and data transferred via communicationsinterface (824) are in the form of signals which may be, for example,electronic, electromagnetic, optical, or other signals capable of beingreceived by communications interface (824). These signals are providedto communications interface (824) via a communications path (i.e.,channel) (826). This communications path (826) carries signals and maybe implemented using wire or cable, fiber optics, a phone line, acellular phone link, a radio frequency (RF) link, and/or othercommunication channels.

In this document, the terms “computer program medium,” “computer usablemedium,” and “computer readable medium” are used to generally refer tomedia such as main memory (810) and secondary memory (812), removablestorage drive (816), and a hard disk installed in hard disk drive (814).

Computer programs (also called computer control logic) are stored inmain memory (810) and/or secondary memory (812). Computer programs mayalso be received via a communication interface (824). Such computerprograms, when run, enable the computer system to perform the featuresof the present invention as discussed herein. In particular, thecomputer programs, when run, enable the processor (802) to perform thefeatures of the computer system. Accordingly, such computer programsrepresent controllers of the computer system.

The flowcharts and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowcharts or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

Alternative Embodiment

It will be appreciated that, although specific embodiments of theinvention have been described herein for purposes of illustration,various modifications may be made without departing from the spirit andscope of the invention. In particular, the system can be configured tomonitor and report power consumption of one or more processing units incommunication with the monitored physical storage devices. Responsive tolowering a power consumption setting of a physical storage device, theprocessing unit in communication with the physical storage device mayalso have an associated power consumption setting lowered. In oneembodiment, the placement of the processing unit into a lowered powerconsumption setting may be in response to the measured power consumptionfeedback and the requirement to further lower the power consumptionassociated with the physical storage devices. Accordingly, the scope ofprotection of this invention is limited only by the following claims andtheir equivalents.

1. (canceled)
 2. (canceled)
 3. (canceled)
 4. (canceled)
 5. (canceled) 6.(canceled)
 7. (canceled)
 8. (canceled)
 9. A system comprising: a storagesubsystem of a data site having multiple storage devices, the devicesorganized into a hierarchy comprised of at least one disk array and atleast one volume; a functional unit in communication with the storagesubsystem, the functional unit comprising: a storage device manager tomonitor and report power consumption of the storage devices; a dataaccess manager to monitor and report data access performance on each ofthe storage devices, including the data access manager to store policiesof the storage devices; a power manager in communication with thestorage device manager and the data access manager to receive thereports, the power manager to employ real-time heuristics to lower powerusage of at least one storage device in the subsystem by at least arequired amount in response to a request to limit power whilemaintaining performance responsive to the stored policies, theheuristics comprising: a first heuristic to select one of the devices inthe hierarchy and lower a power consumption setting of the selecteddevice based upon a priority setting; and a second heuristic to measurepower consumption feedback after the first heuristic lowers the powerconsumption setting of the selected device based upon the prioritysetting, and the second heuristic to adjust selection of the devicesaccording to the measured feedback.
 10. The system of claim 9, whereinthe first and second heuristics dynamically manage power consumption,including temporarily reducing energy consumption of a storage subsystemwhile minimizing overall performance impact.
 11. The system of claim 10,further comprising the first and second heuristics to reduce energyconsumption by manipulating operation of the storage devices, whereinthe manipulation is selected from the group consisting of: throttling anI/O rate to a low important volume, placing the disk array into a lowpower state, and combinations thereof.
 12. The system of claim 10,further comprising the power manager to remove any power consumptionlimitations on all volumes and disk arrays in the hierarchy when therequest to limit power has elapsed.
 13. The system of claim 9, furthercomprising the first and second heuristics to throttle storage volumesin order of priority from a low priority setting to achieve powersavings.
 14. The system of claim 9, wherein the storage subsystem of thedata site is a shared pool of configurable resources.
 15. A computerprogram product for use with a storage subsystem of a data site havingmultiple storage devices organized in a hierarchy comprised of at leastone disk array and at least one volume, the computer program productcomprising a computer readable storage medium having computer readableprogram code embodied thereon, which when executed causes a computer toimplement the method comprising: monitoring and reporting powerconsumption of the storage devices; monitoring and reporting data accessperformance on each of the storage devices; in response to a request tolimit power, employing real-time heuristics receive the reporting and tolower power usage by at least a required amount of at least one storagedevice in the subsystem while maintaining performance based upon storedpolicies, the heuristics comprising: selecting one of the devices in thehierarchy and lowering a power consumption setting of the selecteddevice based upon a priority setting; and measuring power consumptionfeedback after lowering the power consumption setting of the selecteddevice and adjusting selection of the devices according to the measuredfeedback.
 16. The computer program product of claim 15, furthercomprising dynamic management of power consumption, includingtemporarily reducing energy consumption of a storage subsystem whileminimizing overall performance impact.
 17. The computer program productof claim 16, further comprising reducing energy consumption bymanipulating operation of the storage devices.
 18. The computer programproduct of claim 17, wherein the manipulation is selected from the groupconsisting of: throttling I/O rates to a low important volume in thehierarchy, placing the disk array into a low power state, andcombinations thereof.
 19. The computer program product of claim 16,further comprising removing power consumption limitation on all volumesand disk arrays in the hierarchy after the request to limit power haselapsed.
 20. The computer program product of claim 15, furthercomprising the heuristics throttling volumes in order of priority from alow priority setting to achieve power savings.
 21. The computer programproduct of claim 15, wherein the storage subsystem of the data site is ashared pool of configurable resources.
 22. (canceled)
 23. (canceled) 24.(canceled)
 25. (canceled)